[CEL-1560] Allow frozen UI renderer 0.155 alias - #25
Conversation
|
Warning Review limit reachedNext included review available in 26 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughSummary by CodeRabbit
WalkthroughThe workflow allowlists ChangesFrozen renderer validation
Estimated code review effort: 2 (Simple) | ~5 minutes Merge Risk: ⚪ Minimal · up to This change allows the frozen 0.155 renderer alias while preserving existing 0.154 compatibility and adds coverage for the supported manifest and lockfile shapes. No actionable merge-blocking risk remains beyond normal checks and review. Suggested labels: Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Independent review B — REQUEST_CHANGES — SHA P1 — Validator allow-list entry authorizes more than intended frozen alias. Adding Fix: model frozen aliases as exact alias-name/target pairs, separate from general private-package allow-list. Add negative manifest + lock fixtures for direct package, wrong allowed target, and wrong version. Checks: lock validator 29/29 + manifest 48/48; static job boundaries pass; Discord metadata boundary pass. Slop/overfit pass: new happy fixtures cover requested acceptance but omit exclusivity classes above. GitHub disallowed formal request-changes review because authenticated account owns PR; posted comment instead. |
There was a problem hiding this comment.
No issues found across 2 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Auto-approved: Adds the 0.155 frozen renderer alias to static-deploy validators with matching tests, unblocking the consumer pin to @cellarnode/ui@0.155.1.
Re-trigger cubic
|
Independent review, SHA P1: |
|
Independent final review A — APPROVE — SHA P0–P3: none. Frozen aliases map exactly: Checks: |
|
Independent final review B — APPROVE — SHA P0: none. P1: none. P2: none. P3 note: committed happy lock fixture omits real pnpm peer-context suffix; validator regex accepts consumer shape Reproduced: validator fixtures 32/32 lock + 56/56 manifest; static-job boundaries; Discord boundary; |
|
Independent final review B — APPROVE — SHA P0: none. P1: none. P2: none. P3 note: lock alias Reproduced: exact SHA; 33 lock + 60 manifest fixtures; static-job boundaries; Discord boundary; YAML parse; |
|
Independent final review B — APPROVE — SHA P0: none. P1: none. P2: none. P3 note: lock locator peer-context regex accepts arbitrary parenthesized metadata after pinned Reproduced: 35 lock + 66 manifest fixtures; static-job boundaries; Discord boundary; YAML parse; |
|
Independent final review B — APPROVE — SHA P0–P3: none. Reproduced: 36 lock + 74 manifest fixtures; static-job boundaries; Discord boundary; YAML parse; Non-blocking P3 note: peer-context suffix regex remains permissive after exact pinned base locator; frozen install still validates pnpm lock semantics. |
|
Independent final review A — APPROVE — SHA P0–P3: none. Direct frozen mappings exact: Checks: validator fixtures 36 lock + 74 manifest; job-boundaries; Discord boundary; YAML parse; diff check; extracted consumer #207 artifacts; direct-field matrix 20/20. |
|
Independent final review B — APPROVE — SHA P0–P3: none. Reproduced: 40 lock + 74 manifest fixtures; static-job boundaries; Discord boundary; YAML parse; |
Linear: https://linear.app/cellarnode/issue/CEL-1560
Summary
@cellarnode/ui-renderer-0-155in static-deploy manifest and pnpm-lock validators0.154frozen-renderer compatibilitynpm:@cellarnode/ui@0.155.1manifest and lockfile shapesWhy
E-label consumer PR #207 pins scan rendering to published
@cellarnode/ui@0.155.1. Reusable deploy validator currently rejects its frozen alias before install.Test plan
ruby .github/tests/deploy-static-lock-validator.test.rbruby .github/tests/deploy-static-job-boundaries.test.rbruby .github/tests/discord-metadata-boundary.test.rbpackage.jsonandpnpm-lock.yamlMerge order: this guard first; then pin consumer workflow to merged SHA; deploy consumer; widen backend publication allow-list.
Summary by cubic
Allows the static-deploy validator to accept the frozen
@cellarnode/ui-renderer-0-155alias for@cellarnode/ui@0.155.1, and enforces that each frozen renderer alias resolves to its exact pinned target version.0-155alias is allowed in both manifest and lockfile validators, covering thenpm:@cellarnode/ui@0.155.1shape.0-154and0-155aliases now fail if their target version, package, or placement doesn't match the exact pinned value.Written for commit 1badd4f. Summary will update on new commits.